up: embedded systems - bacnet  
embedded systems - bacnet - APDU HeaderWhat links here?
    |-7-|-6-|-5-|-4-|-3-|-2-|-1-|-0-|
    |---+---+---+---+---+---+---+---|
 1: | PDU-type      | s | m | a | 0 |
    |---+---+---+---+---+---+---+---|
 2: | 0 | max seg   | max APDU      |
    |---+---+---+---+---+---+---+---|
 3: | invoke id                     |
    |---+---+---+---+---+---+---+---|


fields
bitsnamedata typedescription
byte 1 bits 7 - 4PDU TypeINTEGERSee table below
byte 1 bit 3sBOOLEANthis is a segmented message
byte 1 bit 2mBOOLEANTRUE if this is a segmented message, and this is not the final segment
byte 1 bit 1aBOOLEANTRUE if the requester will accept a segmented BACnet-Complex-ACK-PDU as a response
byte 1 bit 000not used, must be 0
byte 2 bit 700not used, must be 0
byte 2 bits 6 - 4max segINTEGERthis parameter specifies the maximum number of segments that the device will accept.
byte 2 bits 3 - 0max APDUINTEGERmaximum size of a single APDU (Application Protocol Data Unit) that can be accepted by the device.
byte 3 bits 7 - 0invoke idintegerused to match requests and responses


PDU-Type
0x0XBACnet-Confirmed-Request-PDU
0x1XBACnet-Unconfirmed-Request-PDU
0x2Xembedded systems - bacnet - BACnet-SimpleACK-PDU
0x3XBACnet-ComplexACK-PDU
0x4XSegment ACK
0x5XError-PDU
0x6XReject-PDU
0x7XAbort PDU
0x8X - 0xFXreserved

found this without explanation:
0x02	APDU type 0: Confirmed Request; Bit1: Segmented Response Accepted



embedded systems - bacnet - APDU Header
filename:embedded systems - bacnet - APDU Header
filename:embedded%20systems%20%2D%20bacnet%20%2D%20APDU%20Header
last edit:April 04 2016 21:47:04 (2953 days ago)
ct = 1714969887.000000 = May 06 2024 00:31:27
ft = 1459820824.000000 = April 04 2016 21:47:04
dt = 255149063.000000